SAP Bo Design Studio Interview Questions

SAP Bo Design Studio Interview Questions

Q1. Can Visual Composer applications be migrated to Design Studios?

Ans: With current planning, the answer is no as Design Studio is the premium alternative to WAD/Xcelsius and VC is a different technology. 

Q2. Does the design Studio support Hierarchy?

Ans: Yes, Design Studio supports all OLAP features that BW provides – time-dependent hierarchy, attributes, etc.

Q3. What are the differences between Personal, Shared, and Secured connections?

Ans: A Personal connection is created by one user and cannot be used by other users. The connection details are stored in PDAC.LSI file.

A shared connection can be used by other users through a shared server. The connection details are stored in SDAC.LSI file in the Business Objects installation folder. However one cannot set rights and securities on objects in a shared connection. Neither can a Universe to exported to the repository using a shared connection.

A secured connection overcomes these limitations. Through it, rights can be set on objects and documents. Universes can be exported to the central repository only through a secured connection. The connection parameters, in this case, are saved in the CMS.

Q4. What is a fan trap? How can it be solved?

Ans: In a universe structure, we may have 3 tables joined in such a way that the 1st table has a one-to-many join with the 2nd table, which in turn has a one-to-many join with the 3rd table(A -< B -< C). In such a scenario, if a measure is present in the 2nd table and it is dragged along with any dimension from the 3rd table, the value of the measure will be inflated. Such a condition is known as a fan trap.

A fan trap is solved by creating an alias of the 2nd table and defining contexts such that, the normal table is joined only with the first table, while the alias is joined with both the 1st and the 3rd table. We would take the 2nd table’s measure only from the normal table and other dimensions of the 2nd table from the alias table

Q5. Should we encounter fan traps in a data warehouse scenario? If so, then how?

Ans: If a data warehouse is based on the Kimball model, it is a dimensional schema. In a universe built on that DW, for a fan trap to occur in such a schema, we require a direct join between two fact tables, which is against the principles of dimensional modelling.

On the other hand in a data warehouse based on the Inmon model, it is a normalized schema. Though in such a case, universes are generally designed on Data Marts, which are dimensional schemas (where fan traps should not occur). However, if a universe is built on the DW (for the purpose of operational reporting), then a fan trap can occur in that universe

Q6. What are the 2 different approaches to implementing aggregate awareness? Which one is better in terms of performance?

Ans:

The 2 approaches are as follows:

• Aggregate tables are built in the database, which contains the dimension fields(not foreign keys) along with the aggregated measures. In the universe they are present as standalone tables, i.e. they are not joined with any dimensions. The aggregate aware function is used to define both the dimensions and measures of such tables.
• No aggregate tables are built at the database level. They contain the normal fact table at different granularities. In the universe, aggregate awareness is used only to define the measures and aggregate incompatibility is set accordingly.
• The first approach is better in terms of performance since for the higher levels of aggregation, all the information is obtained for a single table. However, large-scale implementation of this approach in a dimensional schema is difficult. In most BI projects, the second approach is preferred.

Q7. Is this only for BW and OLAP? if yes, is there a plan to use it with other data sources?

Ans: Design Studio 1.1  can connect to BW and HANA as backend systems.  Plan to connect to other data sources such as universes in future releases.  

Q8. When will geo maps/geocoding be added, please?

Ans: This is planned for releases after 1.2 in the backlog.

Q9. Can Design Studio connect to R/3 systems and fetch data from backend tables? If not, are there any alternative tools?

Ans: 1.2 via SDK via web services; or use transient provider today (EHP 5 ECC 6.0 or higher) 

If you want to enrich your career and become a professional in SAP BO, then visit Tekslate - a global online training platform: "SAP BO Training" This course will help you to achieve excellence in this domain.

 

Q10. How can Geo-Maps be integrated into Design Studio? Are there any 3rd party Add-ons that Design Studio support for the same?

Ans: With 1.1 do not have; with 1.2 will not have geo maps; a partner using SDK could do that but the beta program has just started.  

Q11. We are planning to upgrade DS 1.1 with SP02, We noticed that it will only work with Internet Explorer 10.

Ans: Works with IE9 – check the PAM or perhaps put in a support ticket.  

Q12. Is Design Studio using HTML 5 for iPad? Same with the iPhone?

Ans: Yes, exactly; the technology is HTML5 and can deploy on mobile devices.  Deploy on iPhone, iPad, or Mobile BI solution  

Q13. Will it work with other browsers: Firefox, Chrome, etc?

Ans: Yes, will work with other browsers.  For IE need 9 for runtime – check PAM  

Q14. What technology does Design Studio use, which is different from the Dashboard?

Ans: DS is HTML5 based and Dashboard has provided an HTML5 version – answered before, will become one tool in a long-time.  DS is optimized for BW and HANA and will offer support for universes.  

Q15. Do we have bookmark concepts in Design Studio in the future?

Ans: Yes, this is planned for the future as Design Studio is a successor to WAD. 

Q16. How can we make design studio dashboards available on mobile?

Ans: 2 options – 1 for end-users to use the Mobile BI solution using the Bi platform, category mobile to DS application then see it on the mobile app. Developers can do it locally using QR codes  

Q17. Is there a data size limit using Design Studio?

Ans: Cannot generally say limit for that – not like Xcelsiu's limitation.  DS uses the BICS interface to connect to BW / HANA (analytic/calc views).

Q18. For HANA data, the analysis view is the source for a Design Studio? how about other views?

Ans: Calc views can be a data source too.

Q19. Do you have RRI (report-to-report interface) functionality in Design Studio?

Ans: If asking about defined BW – do not have – planned for 1.3 release. if the jump from one app to another can use the OpenDoc link today.  

Q20. Is Ingo’s book coming out besides on Kindle?

Ans. Ingo Hilgefort‘s Design Studio book is only available on the Kindle – you can download a Kindle reader for PC, Cloud reader, iPad, etc.  

Checkout our Blog on SAP BO Tutorial

Q21. How is a derived table different from a view? Which one is a preferred solution?

Ans: A derived table is present only at the universe level, while a view is created at the database level. Generally, views are preferred since in its case the onus of calculation remains on the database and it does not load the BO server. However, in cases where developers do not have access to the database, the derived table is the only solution.

Q22. How can we access one derived table from another?

Ans: We can access one derived table from another using the function @derived_table. The syntax is:

@derived_table(Derived Table Name)

Q23. How can we use index awareness in the universe prompt?

Ans: An extended prompt syntax is available since BO 3.1. It is as follows

@Prompt( ’message’, 'type’, [lov],

mono/multi,

free/constrained/primary_key,

persistent/not_persistent,

{'default value':'default key'} )

If the indexes for the dimension object are defined in the universe and we define the prompt condition on the object with the clause ‘primary key’ in place of free or constrained, then the filter condition will convert the prompt values entered to their corresponding indexes and eliminate the join with the dimension table

Q24. What is a condition object? How is it different from the query filter?

Ans: A condition object is a filter condition created at the universe level. When this object is dragged in the Query Panel, the filter condition appears in the query SQL.

However, a query filter exists in the report only. It is added during building a query. This also appears in the query SQL

Q25. What happens when we click the Include button after linking two universes?

Ans: After creating a link if the ‘Include’ button is clicked then the tables from the core universe are permanently copied into the derived universe and the link is severed

Q26. What are the added features of Interactive mode in Web Intelligence over the normal Java report panel? What are its uses?

Ans: When Web Intelligence is in Interactive mode, one can create variables, input controls, and add report filters, tables, and charts in the view model itself. This is not possible in the normal Java report panel.

The advantage of interactive mode is for power users, who want to do further manipulations on an existing report. Since it does not allow the user to modify queries or existing variables in the report but allows doing the above-mentioned activities on top of the report, it provides a very good means for analysis by the power users without changing the core report in any way.

Q27. What is the difference between Input and Output calculation contexts in a Web report?

Ans: The input context consists of any dimension objects that need to be included directly in the calculation itself.

The output context consists of one or more dimension objects that determine the aggregation level at which the calculation is displayed.

Q28. In Oracle, we use the Instr function to display the position of a character in a string. What is the corresponding BO Web Intelligence report function, that does the same?

Ans: The corresponding function is Pos(). The syntax is:

Post( string input_string; string pattern )

Q29. Suppose in a report, we have a filter on a block. In the table, we need to display an aggregate of a measure for all data in the report. But if we use only the aggregate function, it will be limited by the block filter. How can we achieve that?

Ans: We have to use the NoFilter() function. When we put the expression within NoFilter(), it overrides any report filter as well as ranking applied at the report level. The syntax is :

NoFilter( expression )

Q30. Suppose we want to display the total sum of a measure in the row level of the report block. What will be the solution?

Ans: We have to use context Operator In along with keyword reports. This will give the total sum of the measure in the row level (and anywhere in the report). The expression will be like:

Sum( Measure In Report )

Q31. Which selector gives the option of multiple selections in the Xcelcius Dashboard? How do we make multiple selections?

Ans: Only ‘List Builder’ gives the option of multiple selections in Xcelcius. We select multiple rows from the input list and add them to the output list using the Add button. The output list gives the selection parameter

Q32. Which Xcelcius components can we use for linking multiple dashboard flash outputs(SWF files)? Can the same components be used for a complete presentation?

Ans: We can use ‘Swf Loader’ as well as ‘Slideshow’ components for linking multiple dashboards. ‘Swf Loader’ can open SWF files only, while ‘Slideshow’ can open both SWF files and image files.

For presentation purposes, we often need text and images. Hence these are embedded in image files that are added to a ‘Slideshow’ along with dashboard outputs. Moreover ‘Swf Loader’ can only open SWF through ‘Push Button’ or selector components, whereas ‘Slideshow’ has a feature of automatic slide transition, which loads the image and SWF files in the specified sequence. Hence, ‘Slideshow’ is the only feasible option for a complete presentation.

Q33. What are the different ways in which an Xcelcius dashboard can access data from a BO universe?

Ans: There are 3 ways in which Xcelcius can access data from the universe:

Query as a Web Service: Using Query as a Web Service tool, we can create queries from the universe along with filter conditions. The QAAWS query panel is similar to the Web Intelligence query panel. In the Xcelcius dashboard, we can create a QAAWS connection that would point to a particular Query and import the data into the Excel datasheet of the Xlf

Business Intelligence Web Service: In this method, we can use the output of a report directly in the Xcelcius dashboard. Using Web Rich Client, we export the report to the repository, then select a block from the report, right-click and select Publish as Web Service option. However, BIWS does not have a connection of its own. We access this BIWS through a QAAWS connection only.

LiveOffice: LiveOffice is an additional component that needs to be installed. This creates a sort of plugin for all MS Office applications, through which they can access data from Web Intelligence reports. In MS Excel, we can launch the Live Office Insert Wizard by Insert -> Web Intelligence Content. We can use this wizard to add selective content from a website report. In the Xcelcius dashboard, a Live Office connection is created and access this Live Office Excel sheet through this connection

Q34. What is the use of the scope of analysis pane in the Query tab of the Web report?

Ans: It has 2 uses:

1. The Scope of Analysis pane sets the limit of drill down in the report. Suppose we have a hierarchy defined in 3 levels, but if we set the scope of analysis is set to 2 levels, the report will not be able to drill down to the 3rd level. We can also remove objects showing in the scope of analysis pane and limit the drill-down
2. If the analysis level is set to custom, the objects from existing hierarchies can be dragged into the scope of the analysis panel to set the scope for drill-down in the report. This has the advantage that we can drill down to more than 3 levels, which is not possible in the normal level setting since it is up to 3 only.

Q35. Here is a requirement that in a numeric column of a web report, we need to display the sum of the above rows. Which function should we use?

Ans: In this case, we should use the RunningSum() function. The syntax is:

         RunningSum( [measure] ; [Row|Col] ; [ (reset_dimensions) ] )

Q36. When should we use a query filter and when a report filter?

Ans:

The choice of query or report filter has to take into consideration the performance of the report.

• Suppose we have a report where are multiple tabs having different objects requiring the same or different filter conditions, it is advisable to use a Query Filter.
• In the case where there are multiple tabs having the same objects, but with slightly differing filter conditions, it is advisable to fetch the whole data in the query and then apply report filters to the various tabs to get the desired data instead of using separate queries for each tab.

Q37. Is this only for BW and OLAP? if yes, is there a plan to use it with other data sources?

Ans: Design Studio 1.1  can connect to BW and HANA as backend systems.  Plan to connect to other data sources such as universes in future releases.  

Q38. Does the design Studio support Hierarchy?

Ans: Yes, Design Studio supports all OLAP features that BW provides – time-dependent hierarchy, attributes, etc.

Q39. Can Design Studio connect to R/3 systems and fetch data from backend tables? If not, are there any alternative tools?

Ans: 1.2 via SDK via web services; or use transient provider today (EHP 5 ECC 6.0 or higher)  

Q40. What is the roadmap for supporting BW Integrated Planning? Rough Timeline?

Ans: This is very highly rated in Idea Place – planning to do this in 1.3 next year – can’t promise though

Q41. How can Geo-Maps be integrated into Design Studio? Are there any 3rd party Add-ons that Design Studio support for the same?

Ans: With 1.1 do not have; with 1.2 will not have geo maps; a partner using SDK could do that but the beta program has just started.  

Q42. What is the Design Studio scripting language and where can we find a tutorial, training or reference guide?

Ans: A subset of JavaScript languages; if you know JavaScript you should be fine; provide content assistance with CTRL-SPACE – see help.sap.com for tutorials and examples.  Complex coding – need JavaScript know-how to do that.  

Q43. Can Visual Composer applications be migrated to Design Studios?

Ans: With current planning, the answer is no as Design Studio is the premium alternative to WAD/Xcelsius and VC is a different technology  

Q44. What technology does Design Studio use, which is different from the Dashboard?

Ans: DS is HTML5 based and Dashboard has provided an HTML5 version – answered before, will become one tool in a long-time.  DS is optimized for BW and HANA and will offer support for universes.  

Q45. How can we make design studio dashboards available on mobile?

Ans: 2 options – 1 for end-users to use the Mobile BI solution using the Bi platform, category mobile to DS application then see it on the mobile app. Developers can do it locally using QR codes  

Q46. Is there a data size limit using Design Studio?

Ans: Cannot generally say limit for that – not like Xcelsiu's limitation.  DS uses the BICS interface to connect to BW / HANA (analytic/calc views) –  

Q47. Do you have RRI (report-to-report interface) functionality in Design Studio?

Ans: If asking about defined BW – do not have – planned for 1.3 release. if the jump from one app to another can use the OpenDoc link today  

Q48. Is Ingo’s book coming out besides on Kindle?

Ans: Ingo Hilgefort‘s Design Studio book is only available on the Kindle – you can download a Kindle reader for PC, Cloud reader, iPad, etc.  

Q49. There is a requirement that in a numeric column of a web report, we need to display the sum of the above rows. Which function should we use?

Ans. In this case, we should use the RunningSum() function. The syntax is:

RunningSum( [measure] ; [Row|Col] ; [ (reset_dimensions) ] )

Q50. When should we use a query filter and when a report filter?

Ans. The choice of query or report filter has to take into consideration the performance of the report.

• Suppose we have a report where are multiple tabs having different objects requiring the same or different filter conditions, it is advisable to use a Query Filter.
• In the case where there are multiple tabs having the same objects, but with slightly differing filter conditions, it is advisable to fetch the whole data in the query and then apply report filters to the various tabs to get the desired data instead of using separate queries for each tab.